Return null
when applicable from getGeneratedKeys
#2180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, there is no way to check if
getGeneratedKeys
returnednull
. Instead, when trying to callResultSet.next()
aNullPointerException
is thrown.This method should return an empty
ResultSet
when there are no generated keys, but not all JDBC drivers do (like Apache Derby) In these cases, I think the safest option is to returnnull
, which can then be checked (and is checked in popular JDBC libraries like JOOQ.)